Repository navigation
Update release-plan.yaml for r2.2 - #142
Merged
Merged
Conversation
Contributor
Author
|
@hdamker, may I ask one question as I was asked in another place?
|
Contributor
You have never created the public 0.2.0 yet, but only the pre-release 0.2.0-rc.1 in r2.1. So the next release candidate for 0.2.0 will be 0.2.0-rc.2 in r2.2. In the release-plan.yaml you only need to to change the release tag as you have done, the suffix will be created by Release Automation.
No, 0.2.1 would be wrong as there was never a 0.2.0 version published. |
Contributor
Author
|
Hi @jlurien, could you review this PR? |
jlurien
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
N/A - no upstream issue.
Special notes for reviewers:
Align ReleasePlan yaml file with new Commonalities r4.4 version
target_release_tag: r2.2
commonalities_release: r4.4
target_api_version to 0.2.0 (for both QoS B and QoS B&A APIs)
Changelog input
None
Additional documentation
None